home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000084_kane@sonata.cc.purdue.edu_Tue Oct 26 14:50 MDT 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
4KB
Received: from yvax.byu.edu by maine.et.byu.edu; Tue, 26 Oct 93 14:50:22 -0600
Return-Path: <kane@sonata.cc.purdue.edu>
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H4KLVHRPF48WWJT9@yvax.byu.edu>; Tue, 26 Oct 1993 14:48:18 MDT
Received: from sonata.cc.purdue.edu by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H4KLVB1VAO8Y5IJ7@yvax.byu.edu>; Tue, 26 Oct 1993 14:48:07 MDT
Received: from cantata.cc.purdue.edu by sonata.cc.purdue.edu (5.61/Purdue_CC)
id AA15320; Tue, 26 Oct 93 15:47:59 -0500
Received: by cantata.cc.purdue.edu (NX5.67d/NX3.0X) id AA06354; Tue,
26 Oct 93 15:47:56 -0500
Date: Tue, 26 Oct 1993 15:47:56 -0500
From: kane@sonata.cc.purdue.edu
Subject: miscellanea on README for MiscKit
To: Don_Yacktman@byu.edu
Message-Id: <9310262047.AA15320@sonata.cc.purdue.edu>
Content-Transfer-Encoding: 7BIT
Status: RO
"state the version number of the MiscKit and the object" ->
"state the version number of both the MiscKit and the product" or maybe
product isn't a good word....
I suggest making all the rtf documents < 6 inches in height to fit
on all screens. I don't know if 3.1 will automatically downsize
a window to fit the title bar and the resize bar on the screen--
I haven't had experience with small screens yet.
Otherwise the README looks fine. For best appearance of all
documents, eliminate "excessive" whitespace, or extra whitespace
at the end of the document.
Hmmm, about the License_Notes.rtf (0.6).....
"This document also grants you additional priviledges that are not explicity
listed in the license, so that the MiscKit administrator does not need to
be contacted for special permission as often."
Don't use 'priviledges'. At least: "This document also grants you
some permissions required by the license, so that the MiscKit administrator
need not be contacted for special permission for a few common things."
Or something like that.
"To use it in an app, you should note that you used it somewhere in the app"
Aaaahh! Here's a brain-twister. Hmmm, it doesn't sound better
backwards, either..... :-)
"distribute the MiscKit, you need permission from the MiscKit administrator
only if your distribution falls under one of the categories in point 3;
most distributions will be via ftp or on a floppy from a friend ..."
This paragraph needs correcting, or better, simply remove it. Some
of what it says is said in the license, some is incorrect.
"It is not necessary that you read this entire document..."
You say this twice.
"owner is granting the MiscKit unlimited permission to use the resource"
No, no, no. We'd assign the copyright to you if such were the case.
Only the 4 (or 5) rights named in the license should be repeated here.
I'm sure we don't give you permission to defame our work, for instance
(this is one of a copyright holder's rights, to prevent defamation).
Listing permissions after saying "unlimited" does not have the effect
of limiting permission to them.
The only other thing I read (I have to go to class now) is in point
5 of the Notes, there is an instance of 'should' that should be 'may',
or 'can'. Being black and white (as opposed to wishy-washy) can't hurt.
On license fee restrictions & anti-trust laws, I have gotten one
email response. (I don't forward it, because of copyright questions,
and I don't have the authors permission. Yes copyright is pervasive
and everywhere.) He thought that antitrust laws would not apply
because there is no noticeable restraint of competition (for freely
distributable software). However, the situation is not yet clear,
because precedents have not yet been established by the courts.
Chris